[ci-maintainer] fix(docker): per-attempt timeouts on bobshell download in src/Dockerfile + src/Dockerfile.contributor - #4942
Conversation
…led IBM COS connections retry instead of exhausting the retry budget Three v2 CI runs in ~36h (32990236986, 33072306789, 33132187354) failed in the docker / overlayfs-exec-guard jobs with curl exit 28 while fetching bobshell-1.0.6.tgz from IBM Cloud Object Storage. The curl invocation had --retry-max-time 300 but no per-attempt bound, so one stalled connection consumed the entire retry window and no healthy retry ever happened. - src/Dockerfile (Layer 9): add --connect-timeout 15 --speed-limit 1024 --speed-time 30 --max-time 180 and raise --retry-max-time to 600 so bounded attempts still get a full retry ladder. - src/Dockerfile.contributor: the same bobshell download had no retry or timeout flags at all; bring it up to the same hardened pattern. Refs #4941 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: sec-check <sec-check@hive.kubestellar.io>
kubestellar-prow
Bot
added
the
dco-signoff: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Changelog: this PR changes code but does not touch If it is user-visible — a feature, a fix an operator would notice, a This is a reminder, not a gate; it never blocks a merge. |
kubestellar-prow
Bot
added
the
size/S
|
Thank you for your contribution! Your PR has been merged. Check out what's new:
Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey |
1 participant
CI Fix
Files claimed:
src/Dockerfile(Layer 9, bobshell curl) andsrc/Dockerfile.contributor(bobshell curl) — no overlap with open PRs #4939/#4931/#4923/#4905 (test files) or #4032 (proxy/auth Go code).Three v2 CI runs in ~36h failed in the
docker/overlayfs-exec-guardjobs with curl exit 28 downloadingbobshell-1.0.6.tgzfrom IBM COS (runs 32990236986, 33072306789, 33132187354). The curl had--retry-max-time 300but no per-attempt bound, so one stalled connection burned the whole retry window and curl exited 28 without a healthy retry.Changes:
src/Dockerfile: add--connect-timeout 15 --speed-limit 1024 --speed-time 30 --max-time 180, raise--retry-max-timeto 600; comment documents why.src/Dockerfile.contributor: same bobshell download had no retry/timeout flags at all; hardened to the same pattern.Fixes #4941
Filed by ci-maintainer agent (ACMM L4/L5 — hold-gated mode). Hold-gated: human review required.
— hive: agent=ci-maintainer backend=copilot model=claude-fable-5